Use Azure Federated login mechanism rather than secrets #662
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use federated authentication with GitHub Actions and Azure Entra ID for the Azure login commands during
build-git-installers.yml
builds.This will allow us to drop the use of a client secret to authenticate as the signing identity for Trusted Code Signing.
The
AZURE_CLIENT_ID
,AZURE_TENANT_ID
, andAZURE_SUBSCRIPTION_ID
secrets have already been added to therelease
environment, and a test of theazure/login
step using this mechanism and a subsequentaz
command has been successfully demonstrated here: https://github.com/microsoft/git/actions/runs/9652892561/job/26624014573